NOTE (*): Due to changes done in the following commit https://github.com/cognitedata/service-contracts/commit/191ddb3b200091afa65a3adf9ba2482ff11aa7ed, the types for vision (similar to annotations) were changed from containing 'Cognite' to 'Cogmono'. Not sure what to do here.

It's the teams responsibility to handle these cases; if you rename your types in the service contracts repo it's a breaking change. It's quite easy to forget as this feature isn't enforced in the service contract repo in any way, so we can ping them and see if they want to:

1. rename the types to avoid a breaking change
2. put codegen for vision on pause till later (perhaps there are others that want to do a breaking change as well?)
3. release a major version as they've done some structural breaking changes.

@marvrez @miladcognite could you take a look?

NOTE (*): Due to changes done in the following commit cognitedata/service-contracts@191ddb3, the types for vision (similar to annotations) were changed from containing 'Cognite' to 'Cogmono'. Not sure what to do here.

It's the teams responsibility to handle these cases; if you rename your types in the service contracts repo it's a breaking change. It's quite easy to forget as this feature isn't enforced in the service contract repo in any way, so we can ping them and see if they want to:

1. rename the types to avoid a breaking change
2. put codegen for vision on pause till later (perhaps there are others that want to do a breaking change as well?)
3. release a major version as they've done some structural breaking changes.

@marvrez @miladcognite could you take a look?

The change from 'Cognite' to 'Cogmono' is related to migration (driven by the infra team) of several Python packages to the mono-repo.

I'm not familiar with how we do versioning in the JS SDK, but do you see any issues with releasing a new major version of the SDK?

Sooo, what's the next step to do here? I could disable auto-gen for visions and annotations API such that we can merge the type updates for data modelling

I could disable auto-gen for visions and annotations API such that we can merge the type updates for data modelling

for visions: sounds good to me